Data-fusing activity monitoring device

ABSTRACT

An activity monitoring device accumulates a count of steps taken as an individual bearing the activity monitoring device travels by foot along a route, and wirelessly acquires positioning data from a discrete global-positioning device corresponding to a sequence of locations along the route. The activity monitoring device iteratively revises an estimated stride length of the individual based on the positioning data and the step count and iteratively updates a travel distance on a display of the activity monitoring device according to the step count and the estimated stride length as the individual proceeds from one location in the sequence to the next.

TECHNICAL FIELD

The disclosure herein relates to activity monitoring and moreparticularly to acquiring and displaying activity-related information.

BACKGROUND

Though useful for tracking absolute location and elevation, modernsatellite-based positioning devices tend to be bulky and thus unsuitedto being worn in view (e.g., as wrist-wear, eye-wear or othervisible-at-a-glance accessory) during physically demanding activitiessuch as running or hiking. Also, such devices often fail to provideother types of information desired during physical activity, such asstep count, stair-climb count, calorie burn, heart rate, etc.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure herein is illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings and in whichlike reference numerals refer to similar elements and in which:

FIG. 1 illustrates an exemplary activity tracking sequence carried outcollaboratively by a portable activity-tracking device (also referred toherein as a portable biometric device) and a position-sensing devicehaving GPS (global positioning system) circuitry or othersatellite-based or ground-based global positioning capability;

FIGS. 2, 3A and 3B illustrate an exemplary bonding (or more temporary“pairing”) of the positioning-device and portable activity-trackingdevice and thus, establishment of a trust relationship in which thedevices share collected data with each other;

FIG. 4 illustrates an example of collaborative activity trackingoperation executed by the smartphone and portable activity-trackingdevice of FIG. 1 in greater detail;

FIG. 5 illustrates an example of a data fusion operation executed withinthe above-described portable activity-tracking device (or smartphone)with respect to collaboratively collected data;

FIG. 6 illustrates another data fusion example, in this case reconcilingdiscrepancies in collaboratively collected data and dynamicallycalibrating values used to derive metric data;

FIG. 7 illustrates an example of a dynamic calibration procedure thatmay be executed within the portable activity-tracking device to revise(calibrate) a user's stride length based on incoming GPS data;

FIG. 8 illustrates an exemplary travel distance calculation obtained byfusing GPS data and data acquired from one or more sensors within theportable activity-tracking device;

FIG. 9 illustrates an exemplary set of metrics presented in real-time ona display element of the portable activity-tracking device;

FIG. 10 illustrates an exemplary event loop that may be executed withinthe portable activity-tracking device during an activity trackinginterval; and

FIG. 11 illustrates a generalized embodiment of a portableactivity-tracking device capable of executing the various collaborativeactivity-tracking and fused-data display operations described above.

DETAILED DESCRIPTION

In various embodiments disclosed herein, a portable activity-trackingdevice receives activity-related information from a discretedata-collection device throughout an activity tracking or monitoringinterval and combines the activity-related information with informationobtained from one or more local sensors of the activity-tracking deviceto produce activity metrics for real-time display. In a number ofembodiments, for example, the portable activity-tracking device receivespositional information from a discrete global-positioning devicethroughout the activity tracking or monitoring interval (e.g., while auser is engaged in a physical activity) and combines the positionalinformation with information obtained from one or more local sensors ofthe activity-tracking device for real-time display. By this arrangement,a relatively bulky global-positioning device (e.g., smartphone havingglobal-positioning sensor/circuitry, stand-alone global-positioningdevice or any other electronics device having global or localpositioning capability) may be carried in-pocket or otherwise borne in anot-readily visible location, while a relatively small and lightweightactivity-tracking device presents data collaboratively collected by bothdevices in a real-time, at-a-glance display.

FIG. 1 illustrates an exemplary activity tracking sequence 100 carriedout collaboratively by a portable activity-tracking device 101 (alsoreferred to herein as a portable biometric device or portableactivity-monitoring device) and a position-sensing device 103 having GPS(global positioning system) circuitry or other satellite-based orground-based global positioning capability. For purposes of exampleonly, the portable activity-tracking device is assumed to be awrist-worn device that may be viewed at a glance during physicalactivity of a user/wearer, while the position-sensing device 103 isassumed to be a GPS-enabled smartphone that the user may carry inhis/her pocket, or strap to upper arm or otherwise be borne by the userin a convenient, but not necessarily visible-at-a-glance disposition. Inalternative embodiments, position-sensing device 103 may be a standaloneglobal positioning device or any other user-location-sensing element.Similarly, instead of being worn on the user's wrist, portable-activitytracking device 101 may be worn or carried in-hand, elsewhere in areadily viewable location on the lower or upper arm, or as eye-wear orother head-up type of display. More generally, portableactivity-tracking device 101 may have any form factor and manner ofuser-bearing (transport or carriage) practical for use during theactivity or activities for which it is designed, including attachmentmechanisms for attaching to user equipment such as a bicycle, backpack,etc.

Conceptually, portable activity-tracking device 101 may be viewed ashaving processing circuitry (processor, memory, etc.) to implement anoperating system (OS), sensor circuitry (Snsr) and wirelesscommunication circuitry (WC), together with a user interface (UI) havinga display and tactile input (e.g., one or more buttons, touch-screen,etc.), though one or more sensors within the sensor circuitry may beused to detect gesture input from the user as discussed below and thusconstitute part of the user interface. Portable activity-tracking device101 may also have an interface to enable wired communication (e.g., auniversal serial bus port or other wire interface port). In general, theoperating system executes actions in response to input received from theuser interface (i.e., user input), sensor circuitry and/or communicationcircuitry, and presents activity metrics (i.e., information relating toa user activity such as distance traveled, step count, pace of travel,elevation, stairs climbed, calories burned, heart rate,position/location, activity duration and so forth).

As shown, smartphone 103 (or other positioning device) is assumed tohave a resident operating system (OS) and activity-tracking/logging app(app), both instantiated by program code execution within a processor(i.e., though not specifically shown, the smartphone includes one ormore processors and memory interconnected to form a computing device).Smartphone 103 also includes wireless communication circuitry (WC) forcommunicating information to the portable activity-tracking device, andposition-sensing circuitry (Snsr) such as receiver circuitry forreceiving distance and timestamp information from orbiting satellites(e.g., GPS space vehicles within line of sight at any given time).

As FIG. 1 illustrates, operations involved in collaborative activitytracking via GPS-enabled smartphone 103 and portable activity-trackingdevice 101 (and eventual data archival) may be carried out in phases,including a setup phase 110, initiate-tracking phase 112, collaborativedata collection phase 114, terminate-tracking phase 116 and an optionaldata upload phase 118. In setup phase 110 (i.e., prior to the actualactivity tracking interval as shown at 120), position-sensing device 103and activity-tracking device 101 communicate with one another wirelesslyto confirm a trust relationship, thus pairing or bonding to enablecollaborative activity tracking at a later point in time. As discussedbelow, device pairing or bonding may be carried out throughuser-verification input to each of the two devices (e.g., tactile input,including code or ID entry), or may leverage pre-existing trustrelationships with another entity, such as a server computer in whichboth devices are registered to a given user account or otherwiseassociated with a user or one another.

In initiate-tracking phase 112, user input to portable activity-trackingdevice 101 such as a button push, touch-screen tap or predetermined usermotion (i.e., a “gesture” detected by one or more sensors within theactivity-tracking device) triggers wireless transmission of a data-feedrequest from activity-tracking device 101 to smartphone 103. In oneembodiment, the data-feed request is received via the smartphone'swireless circuitry and forwarded to the smartphone OS which in turnlaunches an activity-tracking app. The activity-tracking app theninteracts with the smartphone OS to request GPS-based position tracking(i.e., regular or intermittent logging of “GPS fix” data, with each suchpositional fix including, for example and without limitation, a GPSlocation and time stamp) and wireless transmission of acquiredpositioning data to activity-tracking device 101. Thereafter, incollaborative data collection phase 114, positioning data capturedwithin smartphone 103 at successive points in time (T_(i), . . . ,T_(j), . . . ) are transmitted to activity-tracking device 101 to befused and/or aggregated with data collected from the activity-trackingdevice's on-board sensors. As shown, the collaboratively collected data(which may be a fusion and/or aggregation of collaboratively collecteddata) is displayed in real-time continuously or in response toview-gestures (discussed below) on a display 121 of activity-trackingdevice 103. At the conclusion of the activity being tracked (e.g.,walking, running, climbing, riding, swimming, rowing, etc.), which maybe explicitly signaled by user input or detected by the collectivesensors of the collaborating devices, activity-tracking device 101issues a stop request to smartphone 103, indicating thatpositioning-data collection and transmission may be stopped. At somelater point in time, collaboratively collected data may be uploaded fromactivity-tracking device 101 and/or smartphone 103 to a general-purposecomputing device (e.g., desktop, laptop, or tablet computer) or servercomputer 123 for archival and more full-featured rendering (e.g.,comparative data display to show differences between activities carriedout at different times or by different individuals, depicting routetraveled during activity on a geographical map and so forth). Forexample, activity-tracking device 101 may upload collaborativelycollected data to smartphone 103 (e.g., to be logged or archived withinactivity-tracking/logging app discussed above) and then communicatedfrom smartphone 103 to computing device/server 123.

While the initiate-tracking phase and terminate-tracking phase aredepicted in FIG. 1 and described in embodiments below as triggered inresponse to input to (or event detection within) portableactivity-tracking device 101, either or both phases may alternatively beinitiated by smartphone/positioning device 103. For example, a user maytap an “initiate-tracking” icon displayed on a touchscreen of smartphone103 by the above-described smartphone app. The smartphone app mayrespond to the tap input by transmitting (via the OS and wirelesscommunication circuitry) a “start-tracking” message to portableactivity-tracking device 101 and communicate a GPS data collectionrequest to the smartphone OS, relaying collected GPS data to portableactivity-tracking device 101 thereafter. Similarly, a stop-tracking icondisplayed by the smartphone app may be tapped to trigger communicationof a terminate-tracking message to portable activity-tracking device 101and a cease-OPS-data-collection message to the smartphone OS. Moregenerally, while collected data is generally described as flowing fromsmartphone 103 (or other positioning device) to portableactivity-tracking device 101, data may additionally or alternativelyflow from portable activity-tracking device 101 to smartphone 103before, during and/or after an activity tracking interval 120.

FIGS. 2 and 3 illustrate an exemplary bonding (or more temporary“pairing”) of smartphone/positioning-device 103 and portableactivity-tracking device 101 and, thus, establishment of a trustrelationship in which the devices share collected data with each other.Referring first to FIG. 2, smartphone 103 and portable activity-trackingdevice 101 are each registered with a network-connected server computer151 (e.g., a “web” server accessible via the Internet and/or othernetwork(s) 153) and thereby associated with one another by the server.For example, the activity-tracking app on the smartphone may include aninterface to enable a user to create an account (i.e., user record) onserver 151 and to register the app and/or smartphone as being associatedwith the user, with a corresponding account credential being supplied toand recorded within the smartphone. The activity-tracking app mayfurther enable the user to identify activity-tracking device 101 (e.g.,by entering a registration key or other information) and associateactivity-tracking device 101 with the user account, or theactivity-tracking device itself may communicate with server 151 via awired or wireless connection. In either case, activity-tracking device101 may be associated with the credential, for example, by receiving thecredential from server 151. Thereafter, smartphone 103 may automatically(or in response to user input) broadcast a bonding/pairing messagebearing the account credential and requesting proximal activity trackingdevices associated with the credential to transmit reciprocalbonding/pairing messages. Upon receiving the broadcast bonding/pairingmessage and confirming association between the activity trackingdevice's own credential and the credential provided in thebonding/pairing message, portable activity-tracking device 101 respondsto the broadcast bonding/pairing message by transmitting abonding/pairing acknowledgment to the smartphone, together with theactivity-tracking device credential to complete the bonding/pairingconnection.

FIG. 3A illustrates an exemplary sequence of operations executed tocarry out the above-described transparent bonding operation. At 231, auser creates an account on a server computer (i.e., network-connectedcomputer), and then indicates a desire to pair or bond anactivity-tracking device to his/her account at 233. A client app on thesmartphone or other positioning device (e.g., the activitytracking/logging app discussed above) receives pairing instructions fromthe server at 235 and then scans for nearby activity-tracking devices at237, for example, by evaluating incoming presence-indicating messages orother signals emitted by in-range activity-tracking devices sua sponteor in response to smartphone request.

Continuing with the bonding/pairing example shown in FIG. 3, auser/wearer of an activity-tracking device proves possession of theactivity-tracking device through a side-channel as shown at 239 (e.g.,by entering a number displayed on the activity-tracking device into thesmartphone client app and/or by performing a motion/gesture with theactivity-tracking device). At 241 the smartphone client app sends theside-band information to the server together with informationidentifying the activity-tracking device (i.e., an activity-trackingdevice ID). The smartphone client app then transmits a message to theactivity-tracking device requesting the activity-tracking device toenter bonding/pairing mode (as shown at 245), and the activity-trackingdevice, upon receiving the bonding request, completes the bonding actionas shown at 247, for example, by communicating a bonding acknowledgmentto the smartphone. Note that the final bonding communication may be alow-level operation managed by the operating systems of the smartphoneand activity-tracking device and thus need not be recorded at the levelof the smartphone client app or server.

FIG. 3B illustrates an alternative exemplary sequence of operationsexecuted to carry out the above-described transparent bonding operation.At 251, a user creates an account on a server computer (i.e., networkconnected computer), registering the smartphone and portableactivity-tracking device. The server then publishes an identifier (ID)of the portable activity-tracking device to the smartphone at 253 andalso publishes an ID of the smartphone of to the portableactivity-tracking device. At 255, an application program executed withinthe smartphone (“smartphone app”) detects user input indicating abonding (or pairing) request and, in response, the smartphone appforwards the bonding request to the OS together with the smartphone IDat 257. The smartphone OS broadcasts the bonding request and ID via thewireless communication circuitry at 259 (e.g., radio communicationcircuitry in accordance with any of various standards such as Bluetooth,Near-field communication, WiFi, WiMax, etc.) and the activity-trackingdevice receives the broadcast at 261. As shown, the activity-trackingdevice confirms the smartphone ID against a list published by theserver, logging the smartphone as a trusted, bonded device. At 263 theactivity-tracking device transmits a bonding acknowledgment message tothe smartphone, the acknowledgement message including theactivity-tracking device ID. The smartphone receives the acknowledgmentmessage at 265 and confirms the activity-tracking device ID against thelist published by the server, recording the activity-tracking device asa trusted, bonded device and thereby completing the transparent bondingoperation.

FIG. 4 illustrates an example of a collaborative activity trackingoperation executed by the smartphone/positioning device 103 and portableactivity-tracking device 101 of FIG. 1 in greater detail. Assuming thetwo devices to have been previously bonded (or paired) and that userinput or other event detection signals the start of a user activity at276 (e.g., the user is starting a run or jog), activity-tracking device101 transmits a GPS data-feed request to smartphone 103 as shown at 275.The smartphone receives the GPS data-feed request at 277 and begins datacollection, acquiring a GPS positional fix (“GPS fix”) at the conclusionof each of a sequence of uniform or time-varying intervals (lntvl 1,Intvl 2, . . . ) and wirelessly transmitting the GPS fix to the portableactivity-tracking device as shown at 283. Note that, though notspecifically shown, at least one GPS fix may be acquired and transmittedto the portable activity-tracking device in immediate response to theGPS data-feed request.

For its part, the portable activity-tracking device accumulates “local”step-count and elevation data from on-board sensors (e.g., accelerometerand altimeter, respectively) as shown at 279 and fuses and/or aggregatesthe local data with incoming GPS data from the smartphone (“remote”data) as shown at 285, logging the fused/aggregated data for continuousor event-triggered presentation on a real-time display (281). As shown,the portable activity-tracking device iteratively fuses and displayscollaboratively collected data during each GPS collection interval,ceasing upon detecting activity-stop input 290 from the user (ordetecting an event that indicates activity cessation). Thereafter, theportable activity-tracking device processes the collaborativelycollected data to produce a finalized, post-activity data set at 291(e.g., generating or refining tallies) and transmits the finalized dataset to the smartphone, optionally archiving the data set within on-boardflash memory or other storage. Upon receiving the finalized data setfrom the portable activity-tracking device, the smartphone maypost-process and/or archive the data set within its own storage as shownat 293 (e.g., for on-demand user viewing) and may also relay thefinalized data set to a server or other computing device for morefull-featured rendering as discussed above.

FIG. 5 illustrates an example of a data fusion operation executed withinthe above-described portable activity-tracking device (or smartphone)with respect to collaboratively collected data. As shown, absoluteelevation information included within each GPS fix (i.e., received fromthe smartphone GPS circuitry/sensor in the example above) is augmentedwith elevation-change information obtained from an altimeter within theportable activity-tracking device (i.e., local sensor) to synthesizemore detailed elevation data than possible with either sensor alone.More specifically, a sequence of altimeter readings (L1Alt[k−1],L1Alt[k], L1Alt[k+1] . . . ) that indicate changes in user elevation(i.e., relative elevation) are added to absolute user elevationspecified in the most recent GPS fix (i.e., Fix[i−1.Elev, Fix[i].Elev,Fix[i+1].Elev, . . . ) to produce more accurate and/or resoluteelevation than possible from either the GPS sensor or altimeter alone.Note that the GPS elevation fix points may themselves be output from afilter (e.g., an infinite impulse response filter, finite impulseresponse filter, common filter, or any other noise filter) as GPSelevation readings tend to be relatively noisy. Also any elevationfiltering may be based on information from both local and remote sensors(e.g., altimeter output of activity tracking device and GPS elevationdata) and/or may be compensated by topological data indexed based onglobal positioning coordinates. In any case, an absolute elevation ofthe user that includes contributions from both theactivity-tracking-device altimeter (e.g., a pressure based sensor and/orgyroscope) and the smartphone GPS data may be displayed in real-time ona display 305 of the activity-tracking device.

FIG. 6 illustrates another data fusion example, in this case reconcilingdiscrepancies in collaboratively collected data and dynamicallycalibrating values used to derive metric data. In the example presented,positional data (i.e., GPS fixes) are assumed to be relativelyinfrequent relative to a user's stride rate. That is, the user takesmultiple (e.g., five, ten or more) strides/steps between successive GPSfix points and thus may round comers or turns that differentiate theactual distance traveled by the user from the distance between GPS fixpoints. Thus, referring to the overhead view of a route traveled by arunner (or walker), it can be seen that the runner makes several turns(shown in regions 325) which lengthen the distance traveled relative tothe Pythagorean distance between any two GPS fix points. Accordingly, atravel distance calculated based on an average stride length and numberof strides taken between any two GPS fix points (i.e., stepcount[i]−step count [i−1] *StrideLen) will, absent other sources oferror, be different from the travel distance indicated by those GPS fixpoints. While this problem may be avoided by increasing the GPSacquisition rate (i.e., to a frequency sufficient that corner roundingmay be neglected), it may in some cases or applications to maintain therelatively low GPS acquisition rate (e.g., for power savings) and/orregular GPS fixes may not be available (e.g., in case of travel in an“urban canyon” between large buildings or otherwise obstructed travelpath). In those cases, local sensors within the portableactivity-tracking device may be used to distinguish cornering/turningfrom straight-line travel (e.g., using stereo accelerometers, gyro,compass, etc.) and thus enable selection of GPS points acquired alongknown straight-line travel paths (e.g., as shown at 327) for augmentedtravel-distance measurement and stride-length calibration. In theexample shown, the sensor output of the activity-tracking device (whichmay include merged data from two or more local sensors as mentioned)includes an acceleration spike 331 for each step taken, together with alower frequency amplitude variation that increases during corneringmaneuvers and decreases during straight line travel. Theactivity-tracking device may thus apply incoming sensor data (which maybe a tuple or vector containing data from multiple sensors) against oneor more thresholds to identify straight line travel paths.

FIG. 7 illustrates an example of a dynamic calibration procedure thatmay be executed within the portable activity-tracking device to revise(calibrate) a user's stride length based on incoming GPS data. Startingat 371, upon detecting a straight line travel path spanning two or moreGPS fix points, the portable activity-tracking device calculates thedistance traveled over the straight-line path based on both step count(multiplied by average stride length) and GPS positional offsets at 373(Pythagorean distance between the two or more GPS fix points) and at 375updates the average stride length (and optionally the average pace)based on the ratio of the OPS-indicated distance and the step-indicateddistance. As shown, the newly calculated average stride length updatemay be input to a filter (e.g., an infinite impulse response filter) toavoid abrupt changes and dithering in average stride length.

FIG. 8 illustrates an exemplary travel distance calculation obtained byfusing GPS data and data acquired from one or more sensors within theportable activity-tracking device. At 381, the portableactivity-tracking device acquires an updated GPS fix (GPS Fix[j]). At383, the portable activity-tracking device evaluates local sensor dataat to determine if the sensor data indicates straight-line travelbetween the newly acquired GPS fix and the immediately prior GPS fixpoint (i.e., GPS Fix[j] and GPS Fix[j−1]). If so, then the Pythagoreandistance between the GPS fix points is used to update the total distancetraveled by the user at 385. Otherwise, if the sensor data does notindicate straight-line travel between the most recently acquired GPS fixpoints, the net travel distance is updated based on the product of theaverage stride length and step count between the two GPS fix points asshown at 387.

FIG. 9 illustrates an exemplary set of metrics presented in real-time ona display element 391 of a portable activity-tracking device. As shown,the displayed metrics may be categorized as fused data metrics 392 thatinclude contributions from local and remote sensors (e.g.,activity-tracking device accelerometer and smartphone GPS circuitry),and aggregated data metrics 394 that are generated based on either localsensor data or remote sensor data, but not both. Thus, distance, paceand elevation may be generated based on fused data (e.g., as discussedabove), while step count, calorie burn and heart rate may be generatedbased exclusively on activity-tracking device sensor information and,conversely, global position (“Location”) may be based exclusively on oneor more GPS fix points received from the smartphone. Numerous othermetrics may be presented based on fused and/or aggregated data inalternative embodiments.

FIG. 10 illustrates an exemplary event loop that may be executed withinthe portable activity-tracking device during an activity trackinginterval. That is, following an activity-start indication (420) andafter issuing or receiving a data-feed instruction 421 to/from thecollaborating device (e.g., from portable-activity tracking device tosmartphone or other positioning device or vice-versa), the portableactivity-tracking device begins logging data obtained from local sensorsas described above and responding to events detected at 423. Forexample, upon detection of incoming GPS data at 425, the portableactivity-tracking device fuses (and/or reconciles and/or aggregates) thelocal and remote data as shown at 427 and stores the result in a datalog (i.e., a database of metrics to be occasionally or continuouslyrendered onto the real-time display of the portable activity-trackingdevice).

Continuing with the various events that may be detected, if the portableactivity-tracking device determines that the activity has paused at 429(e.g., based on local and/or remote sensor data and/or user-input), thedevice may update an internally maintained operating mode to reflect thepause event as shown at 431 and may also display an activity-pausemessage to the user. Similarly, if in an activity-pause mode, sensorinput and/or user-input indicating that the activity being tracked hasre-started may trigger a converse update to the operating mode(switching back from activity-pause mode to activity-tracking mode) andcorresponding re-start message display.

In one embodiment, the portable activity-tracking device is capable ofoperating in a low-power “display-on-demand” mode in which the displayis disabled pending user-input indicating a desire to viewactivity-tracking metrics. For example, when operating in such a mode, aforearm-raising “view gesture” (e.g., raising a wrist-worn device toviewable height and orientation) may be sensed by an accelerometerand/or other local sensors of the portable activity-tracking device asshown at 433 and used to trigger power-up of the device display, therebydisplaying logged activity-tracking metrics to the user in response tothe view gesture (435). Though not specifically shown, a countervailinggesture (e.g., lowering the forearm) may be used to disable the displayand thus preserve battery power.

In a continuous display mode, the displayed metrics may be updated asshown at 439 (i.e., based on logged data) in response to detectingexpiration of an interval timer at 437. For example, the display may beupdated every 60 milliseconds or so and thus continuously from a user'sperspective.

Still referring to FIG. 10, if power within the collaborating device isdetermined to fall below a threshold as shown at 441 (including azero-power threshold at which the collaborating device simply shutsoff), the portable activity-tracking device may disable data collectionwithin the collaborating device (443) and update its internal operatingmode to track user activity according to local sensor input only andthus potentially according to different tracking algorithms orheuristics.

Upon detecting user input at 445, the portable activity-tracking deviceprocesses the user input and takes responsive action at 447, includingstopping activity tracking at 470, changing tracking mode, display mode,etc. Where the user input indicates that activity tracking is tocontinue without further collaborative data collection, the portableactivity-tracking device may send a message to the collaborating deviceinstructing that further data collection may be suspended.

If the power threshold of the portable activity-tracking device isitself determined to fall below a programmed or otherwise predeterminedthreshold (affirmative determination at 449), the local device maytransmit a message to the collaborative device instructing that deviceto proceed with data logging as shown at 451 (including logging datathat had been omitted in view of counterpart data logging within theportable activity-tracking device) and then display a shutdown messageto the user.

If the portable-activity tracking device receives an abort message fromthe collaborating device indicating that activity-tracking is to beaborted (453), the portable activity-tracking device may transmit anacknowledgment to the collaborating device as shown at 455 and displayan activity-stop message to the user.

Similarly, if the portable activity-tracking device detects (e.g., viasensor input or otherwise) that the activity being tracked has ceased asshown at 457 (i.e., paused for a threshold period of time), the portableactivity-tracking device may transmit a message to the collaboratingdevice to disable data collection and/or transmission therein and mayalso display an activity-stop message (459).

FIG. 11 illustrates a generalized embodiment of a portableactivity-tracking device 500 capable of executing the variouscollaborative activity-tracking and fused-data display operationsdescribed above. As shown, portable activity-tracking device 500includes a processing unit 501, memory 503 for storing program codeexecuted by the processing unit to effect the various methods andtechniques of the above-described embodiments. Note that the processingunit itself may be implemented by a general or special purpose processor(or set of processing cores) and thus may execute sequences ofprogrammed instructions to effectuate the various activity-trackingoperations described above (including related setup and data uploadphases).

Still referring to FIG. 11, activity-tracking device 500 furtherincludes one or more sensors 509 as described above (e.g.,accelerometer, altimeter, compass, gyroscope, heart-rate monitor,temperature sensor, optical or auditory sensors and so forth),input/output (I/O) ports 505 for receiving and outputting data(including wireless communication circuitry as described above), and auser interface 507 having, for example and display and tactileuser-input elements (touchscreen, buttons, etc.) to enable a user tocontrol operation of the activity-tracking device as described above.Though not shown, numerous other functional blocks may be providedwithin activity-tracking device 500 according to specialized functionsintended to be carried out by the device and/or intended operatingenvironment. Further, the functional blocks within activity-trackingdevice 500 are depicted as being coupled by a communication path 502which may include any number of shared or dedicated buses or signalinglinks. More generally, the functional blocks shown may be interconnectedin a variety of different architectures and individually implemented bya variety of different underlying technologies and architectures. Withregard to the memory architecture, for example, multiple differentclasses of storage may be provided within memory 503 to store differentclasses of data. For example, memory 503 may include non-volatilestorage media such as fixed or removable semiconductor-based storagemedia to store executable code and related data, volatile storage mediasuch as static or dynamic RAM and so forth.

The various activity-tracking data structures, methods and techniquesdisclosed herein may be implemented through execution of one or moresequences of instructions (i.e., software program(s)) within a computersystem, or by a custom-built hardware ASIC (application-specificintegrated circuit), or programmed on a programmable hardware devicesuch as an FPGA (field-programmable gate array), or any combinationthereof within or external to the computer system.

When received within a computer system via one or more computer-readablemedia, such data and/or instruction-based expressions of the abovedescribed circuits and functional blocks can be processed by aprocessing entity (e.g., one or more processors) within the computersystem in conjunction with execution of one or more other computerprograms including, without limitation, net-list generation programs,place and route programs and the like, to generate a representation orimage of a physical manifestation of such circuits. Such representationor image can thereafter be used in device fabrication, for example, byenabling generation of one or more masks that are used to form variouscomponents of the circuits in a device fabrication process.

In the foregoing description and in the accompanying drawings, specificterminology and drawing symbols have been set forth to provide athorough understanding of the disclosed embodiments. In some instances,the terminology and symbols may imply specific details that are notrequired to practice those embodiments. For example, any of the specificdimensions, form factors, signal path widths, signaling or operatingfrequencies, component circuits or devices and the like can be differentfrom those described above in alternative embodiments. Additionally,links or other interconnection between system components or internalcircuit elements or blocks may be shown as buses or as single signallines. Each of the buses can alternatively be a single signal line, andeach of the single signal lines can alternatively be buses. Signals andsignaling links, however shown or described, can be single-ended ordifferential. A signal driving circuit is said to “output” a signal to asignal receiving circuit when the signal driving circuit asserts (orde-asserts, if explicitly stated or indicated by context) the signal ona signal line coupled between the signal driving and signal receivingcircuits. The term “coupled” is used herein to express a directconnection as well as a connection through one or more interveningcircuits or structures. Device “programming” can include, for exampleand without limitation, loading a control value into a register or otherstorage circuit within the integrated circuit device in response to ahost instruction (and thus controlling an operational aspect of thedevice and/or establishing a device configuration) or through a one-timeprogramming operation (e.g., blowing fuses within a configurationcircuit during device production), and/or connecting one or moreselected pins or other contact structures of the device to referencevoltage lines (also referred to as strapping) to establish a particulardevice configuration or operation aspect of the device. The terms“exemplary” and “embodiment” are used to express an example, not apreference or requirement. Also, the terms “may” and “can” are usedinterchangeably to denote optional (permissible) subject matter. Theabsence of either term should not be construed as meaning that a givenfeature or technique is required.

Various modifications and changes can be made to the embodimentspresented herein without departing from the broader spirit and scope ofthe disclosure. For example, features or aspects of any of theembodiments can be applied in combination with any other of theembodiments or in place of counterpart features or aspects thereof.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

1-22. (canceled)
 23. A method of operating an activity monitoringdevice, the method comprising: obtaining activity data from one or moresensors of the activity monitoring device regarding an activity of auser associated with the activity monitoring device; wirelesslyreceiving positioning data of the user from a discrete data-collectiondevice to the activity monitoring device; calculating an activity metricbased at least in part on the positioning data from the discretedata-collection device and based at least in part on the activity datafrom the activity monitoring device; and causing the activity metric tobe displayed on a display of the activity monitoring device.
 24. Themethod of claim 23, wherein the discrete data-collection devicesincludes a discrete global-positioning device.
 25. The method of claim23, wherein obtaining activity data from the one or more sensorsincludes obtaining a step count of the user from one or moreaccelerometers.
 26. The method of claim 25, further comprising: updatinga stride length of the user based at least on the step count and thepositioning data.
 27. The method of claim 26, wherein the updated stridelength is based on a ratio between a GPS-indicated distance using thepositioning data and a step-indicated distance using the step count. 28.The method of claim 23, wherein the activity metric includes distancetraveled, pace of travel, elevation data, or combinations thereof. 29.The method of claim 23, wherein causing the activity metric to bedisplayed on the display includes causing fused data metrics andaggregated data metrics to be displayed on the display, wherein thefused data metrics include contributions from both the activity data andthe positioning data, and wherein the aggregated data metrics includecontributions from either the activity data or the positioning data. 30.The method of claim 23, further comprising: iteratively updating theactivity metric in real-time on the display of the activity monitoringdevice.
 31. The method of claim 23, further comprising: receiving aninstruction to monitor activity of the user; and causing the discretedata-collection device to transmit positioning data to the activitymonitoring device in response to receiving the instruction to monitoractivity of the user.
 32. A method of operating an activity monitoringdevice, the method comprising: obtaining change in elevation data fromone or more sensors of the activity monitoring device of a userassociated with the activity monitoring device; wirelessly receivingabsolute elevation information from a discrete global-positioning devicefor a sequence of points traveled by the user; calculating a synthesizedabsolute elevation of the user based at least in part on the absoluteelevation information from the discrete global-positioning device andbased at least in part on the change in elevation data from the activitymonitoring device; and causing the synthesized absolute elevation of theuser to be displayed on a display of the activity monitoring device. 33.The method of claim 32, wherein calculating the synthesized absoluteelevation of the user includes updating the absolute elevationinformation with the change in elevation data across a sequence ofreadings from the one or more sensors.
 34. The method of claim 32,wherein the one or more sensors include one or more altimeters.
 35. Themethod of claim 32, further comprising: obtaining a step count of theuser from one or more accelerometers of the activity monitoring device;wirelessly receiving positioning data of the user from the discreteglobal-positioning device; and causing aggregated data metrics to bedisplayed on the display of the activity monitoring device, wherein theaggregated data metrics include contributions from either the step countor the positioning data.
 36. The method of claim 35, further comprising:calculating a distance traveled or pace of travel based at least in parton the positioning data from the discrete global-positioning device andbased at least in part on the step count from the activity monitoringdevice; and causing fused data metrics to be displayed on the display ofthe activity monitoring device, wherein the fused data metrics includecontributions from both the step count and the positioning data.
 37. Themethod of claim 32, further comprising: receiving an instruction tomonitor activity of the user; and causing the discreteglobal-positioning device to transmit the absolute elevation informationto the activity monitoring device in response to receiving theinstruction to monitor activity of the user.